ci: pin GitHub Actions to commit SHAs#5
Merged
Merged
Conversation
Replace mutable version tags (@v6, @v2, @v5) with the commit SHA each tag currently resolves to, keeping the version as a trailing comment so Dependabot can still propose bumps. Pinning the third-party action (oven-sh/setup-bun) closes a supply-chain vector where a repointed tag would execute in CI; the first-party actions/* are pinned for consistency. - actions/checkout v6 -> df4cb1c069e1874edd31b4311f1884172cec0e10 - oven-sh/setup-bun v2 -> 0c5077e51419868618aeaa5fe8019c62421857d6 - actions/cache v5 -> 27d5ce7f107fe9357f9df03efb73ab90386fccae
danny-avila
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins the actions in both workflows to the commit SHA each tag points at right now, version left as a trailing comment so Dependabot can still bump them.
actions/checkoutdf4cb1c069e1874edd31b4311f1884172cec0e10oven-sh/setup-bun0c5077e51419868618aeaa5fe8019c62421857d6actions/cache27d5ce7f107fe9357f9df03efb73ab90386fccaethe only one that really matters is
oven-sh/setup-bun, it's third-party so a repointed tag would run in CI. theactions/*ones are github-owned, pinned just for consistency. blast radius is small anyway, CI runs with a read-only token and there are no actions secrets in the repo.heads up, this repo is published from the ai monorepo so the next sync will revert these unless the same pin lands upstream. not enforcing sha pinning at the repo level for that reason, the branch protection + required checks cover main either way.